Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@web/templates/web/study/create_group.html`:
- Line 13: Add aria-hidden="true" to the decorative <i> icons so they are
ignored by assistive tech; specifically update the <i class="fas fa-users
text-2xl text-green-600 dark:text-green-400"> element and the other decorative
<i> elements referenced around lines 21 and 52 to include aria-hidden="true" (or
an equivalent attribute) while leaving semantic labels for real controls
unchanged so visual appearance stays the same but screen readers won't announce
them.
- Around line 34-47: The template renders form fields using raw widgets
(references: form, field, field.field.widget.input_type, field.id_for_label) and
relies on a large inline <style> block; remove that custom CSS and instead add
Tailwind utility classes to the form widgets via their widget attrs in the form
definition (or Form __init__) so templates only output {{ field }} with
Tailwind-styled widgets, update label markup to use the same Tailwind classes
shown (e.g., block/text-sm/font-medium/mb-1.5 and inline-flex/items-center/gap-3
for checkboxes), and then delete the inline style block (lines 67-166) from the
template to comply with the Tailwind-only rule.
- Line 60: The primary submit button in create_group.html currently uses green
utility classes (e.g., bg-green-600 hover:bg-green-700 active:bg-green-800) —
replace that class attribute on the submit button element with the project
primary button classes: "bg-teal-300 hover:bg-teal-400 text-white px-6 py-2
rounded-lg transition duration-200" (keep any necessary focus/outline classes
like focus:outline-none and focus:ring-* if present).